This repository has been archived by the owner on Sep 5, 2018. It is now read-only.
Bugfix/sqlite #13
Open
Bugfix/sqlite #13
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
added 4 commits
August 31, 2016 13:00
On virtual box the use of eth1 will allow this to run. This not likely to happen in AWS
In virtual box the need for http auth doesn't make sense. Information to allow users to opt out of these
In order to allow Virtualbox to work some addition configurations will need to be made before launching vagrant
Need to investigate why the sqlite is not creating a db correctly.
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Improved documentation around the eth{0/1}
also documented steps to eliminate http basic auth in Virtualbox
I will continue to look into why it doesn't create the sqlite3 database correctly.